Systems and Methods of Adaptive Frame Structure for Time Division Duplex

ABSTRACT

A time division duplex (TDD) scheduling interval communicating transmissions in a first direction may include one or more regions for communicating in a second direction, where the first direction is a transmit direction and the second direction is a receive direction, or vice versa. A radio frame may include TDD scheduling intervals with such regions and/or TDD scheduling intervals without such regions for wireless communication, and these TDD scheduling intervals may further be configured in accordance with different frame structure configurations, such as different scheduling interval lengths, subcarrier spacings or symbol durations.

This application is a continuation of International Application No.PCT/US2016/033436, filed May 20, 2016, which claims priority to U.S.patent application Ser. No. 15/078,621, filed on Mar. 23, 2016 andentitled “Systems and Methods of Adaptive Frame Structure for TimeDivision Duplex”, which claims priority to U.S. Provisional ApplicationNo. 62/168,616, filed on May 29, 2015 and entitled “Systems and Methodsof Adaptive Frame Structure for Time Division Duplex”, all of which arehereby incorporated by reference herein as if reproduced in theirentirety.

TECHNICAL FIELD

The present application relates to wireless communications, andspecifically, methods and systems of adaptive frame structure for timedivision duplex.

BACKGROUND

In a wireless communications system, transmissions are generallycommunicated in accordance with pre-defined fixed frame structures.Fixed frame structures are used so that communicating devices haveknowledge of resources, such as time, frequency, or time and frequencyresources; and interferences between different resources and betweentransmitting and receiving of signals may be avoided or reduced. Modernwireless networks are increasingly used to support communications ofdiverse traffic types. Different traffic types may have differentcharacteristics and quality of service (QoS) requirements, such aslatency, which fixed frame structures may be unable to accommodate.Accordingly, adaptive frame structures capable of efficiently supportingdifferent traffic types are desired.

SUMMARY OF THE INVENTION

Technical advantages are generally achieved, by embodiments of thisdisclosure which describe system and methods of adaptive frame structurefor time division duplex.

In accordance with an embodiment, a method for wireless communicationsis provided. The method includes communicating, by a device, a firstdata transmission in a first time division duplexing (TDD) schedulinginterval in a first direction. The first TDD scheduling interval isconfigured with a first frame structure configuration. The methodfurther includes communicating, by the device, a second datatransmission in the first TDD scheduling interval in a second direction.One of the first direction and the second direction is a transmitdirection, and the other of the first direction and the second directionis a receive direction.

In accordance with another embodiment, a method for wirelesscommunications is also provided. The method includes assigning, by anetwork controller, a frame structure configuration for communicating ina time division duplexing (TDD) scheduling interval in a first directionover a frequency sub-band. The frame structure configuration correspondsto a set of frame parameters. The method further includes selecting, bythe network controller, a switching type for the TDD schedulinginterval. The switching type indicates whether or not the TDD schedulinginterval includes at least one transmission opportunity forcommunicating in a second direction. One of the first direction and thesecond direction is a transmit direction, and the other of the firstdirection and the second direction is a receive direction. The methodalso includes sending an indication indicating communication oforthogonal frequency division multiplexing (OFDM) signals in the TDDscheduling interval in accordance with the set of frame parameters andthe selected switching type.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, and theadvantages thereof, reference is now made to the following descriptiontaken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of an embodiment wireless communicationsnetwork;

FIG. 2A is a diagram of an embodiment downlink TDD TTI;

FIG. 2B is a diagram of another embodiment downlink TDD TTI;

FIG. 3A is a diagram of an embodiment uplink TDD TTI;

FIG. 3B is a diagram of another embodiment uplink TDD TTI;

FIG. 3C is a diagram of another embodiment uplink TDD TTI;

FIG. 3D is a diagram of another embodiment uplink TDD TTI;

FIG. 4 is a diagram of another embodiment downlink TDD TTI;

FIG. 5 is a diagram of another embodiment uplink TDD TTI;

FIG. 6 is a diagram of embodiment TDD TTIs with different framestructure configurations and switching types;

FIG. 7 is tables for representing different frame structureconfigurations and switching types;

FIG. 8 is another table for representing different frame structureconfigurations and switching types;

FIG. 9 is a diagram of an embodiment TDD frame;

FIG. 10 is a diagram of another embodiment TDD frame;

FIG. 11 is a diagram of yet another embodiment TDD frame;

FIG. 12 is a diagram of yet another embodiment TDD frame;

FIG. 13 is a diagram of yet another embodiment TDD frame;

FIG. 14 is a diagram of yet another embodiment TDD frame;

FIG. 15 is a diagram of a TDD frame using special OFDM symbols to alignGPs across frequency sub-bands;

FIG. 16 is a diagram of yet another embodiment TDD frame;

FIG. 17 is a diagram of a method for wireless communications;

FIG. 18 is a block diagram of an embodiment processing system; and

FIG. 19 is a block diagram of a transceiver.

Corresponding numerals and symbols in the different figures generallyrefer to corresponding parts unless otherwise indicated. The figures aredrawn to clearly illustrate the relevant aspects of the embodiments andare not necessarily drawn to scale.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The making and using of embodiments are discussed in detail below. Itshould be appreciated, however, that the concepts disclosed herein canbe embodied in a wide variety of specific contexts, and that thespecific embodiments discussed herein are merely illustrative and do notserve to limit the scope of the claims. Further, it should be understoodthat various changes, substitutions and alterations can be made hereinwithout departing from the spirit and scope of the appended claims.

In the present disclosure, a “transmission time interval” (TTI) or“scheduling interval” corresponds to the interval between the beginningof the time scheduled by an instance of scheduling control signaling,and the beginning of the time scheduled by the next instance ofscheduling control signaling. The duration of a scheduling interval canbe measured or specified in units of time (e.g., 1 ms) or in symbols(e.g., 14 OFDM symbols). The duration of a scheduling interval can befixed or configurable, and may vary depending on other wirelesscommunication parameters such as subcarrier spacing.

Embodiments described herein communicate data transmissions in oppositedirections in the same time division duplex (TDD) transmission timeinterval (TTI). In one example, a downlink TDD TTI includes a region foruplink transmissions. In another example, an uplink TDD TTI includes aregion for downlink transmissions. Regions in a TDD TTI that carrytransmissions in an opposite direction than that of the TDD TTI areherein referred to as opposite regions. An opposite region in a TDD TTImay carry data (i.e., an opposite data region) and/or feedbackinformation (i.e., an opposite feedback region), such as a HybridAutomatic Repeat reQuest (HARD) acknowledgement (ACK)/negativeacknowledgement (NACK) message. In one example, a TDD TTI may includeone opposite region for carrying data, and another opposite region forcarrying feedback information. In such an example, the opposite regionsmay span different time-domain resources or different frequency-domainresources.

Embodiments of the present disclosure also provide systems and methodsfor communicating orthogonal frequency-division multiplexing (OFDM)signals in a TDD frame having TDD TTIs configured with different framestructure configurations and TTI switching types. As used herein, a TDDframe refers to a frame that carries signals in TDD TTIs. The differentframe structure configurations may utilize different sets of frameparameters including a sub-carrier (SC) spacing, a TTI length, a cyclicprefix (CP) length, and a symbol duration. Different TTI switching typesindicate different configurations of opposite data regions and oppositefeedback regions included in TDD TTIs. In one embodiment, TDD TTIs inthe TDD frame over different OFDM frequency sub-bands have different TTIlengths and/or different subcarrier spacings. In another embodiment, TDDTTIs in the TDD frame over the same OFDM frequency sub-band havedifferent TTI lengths and/or different subcarrier spacings. In yetanother embodiment, TDD TTIs in the TDD frame over different OFDMfrequency sub-bands are configured to have different TTI switchingtypes. In yet another embodiment, TDD TTIs in a frame over the same OFDMfrequency sub-band are configured to have different TTI switching types.In yet another embodiment, a TDD TTI in the TDD frame includes zero,one, or more opposite regions. Guard periods (GPs) are included in a TDDframe to separate downlink and uplink transmissions and are aligned inthe time domain across frequency sub-bands. Configuration information ofa TDD TTI, such as frame structure configuration, TTI switching type,and frequency sub-band of the TDD TTI, may be pre-defined, defineddynamically or semi-statically, and signaled to UEs. The signaling maybe transmitted through broadcast, multicast or unicast dynamically,semi-statically or statically.

FIG. 1 is a network 100 for communicating data. The network 100comprises a base station 110 having a coverage area 101, a plurality ofmobile devices 120, and a backhaul network 130. As shown, the basestation 110 establishes uplink (dashed line) and/or downlink (dottedline) connections with the mobile devices 120, which serve to carry datafrom the mobile devices 120 to the base station 110 and vice-versa. Datacarried over the uplink/downlink connections may include datacommunicated between the mobile devices 120, as well as datacommunicated to/from a remote-end (not shown) by way of the backhaulnetwork 130. As used herein, the term “base station” refers to anycomponent (or collection of components) configured to provide wirelessaccess to a network, such as an enhanced base station (eNB), amacro-cell, a femtocell, a Wi-Fi access point (AP), or other wirelesslyenabled devices. Base stations may provide wireless access in accordancewith one or more wireless communication protocols, e.g., long termevolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA),Wi-Fi 802.11a/b/g/n/ac, etc. As used herein, the term “mobile device”refers to any component (or collection of components) capable ofestablishing a wireless connection with a base station, such as a userequipment (UE), a mobile station (STA), and other wirelessly enableddevices. In some embodiments, the network 100 may comprise various otherwireless devices, such as relays, low power nodes, etc.

Although the network 100 is shown having a single base station 110, itshould be understood that the network 100 may include multiple basestations 110. The operations of one or more of the base stations 110 maybe controlled by a controller that is either collocated with one of thebase stations 110 or located elsewhere in the network in communicationwith the one or more base stations 110.

Transmissions between a base station and a mobile device are generallycommunicated in transmission time intervals (TTIs) (or “subframes”) inaccordance with pre-defined frame structure configurations. As usedherein, “communicating a transmission” refers to transmitting orreceiving the transmission. The transmissions may include data, controlinformation, and/or feedback information, such as Hybrid AutomaticRepeat reQuest (HARD) acknowledgement (ACK)/negative acknowledgement(NACK) messages. A frame structure configuration generally specifies acombination of frame parameters, such as sub-carrier (SC) spacing, TTIlength, cyclic prefix (CP) length, and symbol duration. The lengths ofTTIs affect latency performance and throughput performance of a network.Specifically, shorter TTIs achieve superior latency performance byproviding more frequent transmission opportunities, and longer TTIsachieve superior throughput performance by reducing signaling overhead.

Generally, a TTI is designated for transmissions in either an uplinkdirection or a downlink direction, which may be referred to astransmission direction of the TTI, and thus a TTI may be referred to asan uplink TTI or a downlink TTI. In some embodiments, a TTI may beconfigured to include a region for transmissions in a direction oppositeto the TTI's transmission direction. For example, a downlink TTIcontains a region for an uplink transmission, or an uplink TTI containsa region for a downlink transmission.

FIG. 2A is an embodiment downlink TTI 200 in a time division duplex(TDD) communications network. The TDD TTI 200 includes regions foruplink transmissions. As shown, the downlink TDD TTI 200 includesregions 201-206 divided in the time domain. The region 201 is allocatedfor downlink control channels, which may be used, for example, to sendscheduling information for uplink data transmissions. The region 202 isfor downlink data transmissions, which may be scheduled or grant-freetransmissions. The region 204 is allocated for an uplink datatransmission, and the region 205 is for transmission of uplink feedbackinformation, such as an uplink ACK/NACK message acknowledging receipt ofa previous downlink data transmission. For example, the uplink ACK/NACKmessage is communicated to acknowledge receipt of a downlink datatransmission communicated in a previous downlink TDD TTI or in theregion 202 of the downlink TDD TTI 200. As used herein, the region 204is referred to as an opposite data region of TDD TTI 200, and the region205 is referred to as an opposite feedback region of TDD TTI 200.

In the example shown in FIG. 2A, the region 204 and the region 205 aredivided in the time domain, i.e., the uplink data transmission in theregion 204 and the uplink ACK/NACK message in the region 205 arecommunicated in a time division multiplexed fashion. The regions 204 and205 may be viewed as uplink transmission opportunities (TOs) for uplinktransmissions of, e.g., low latency uplink traffic or ACK/NACK messages,and may contain one or more orthogonal frequency division multiplexing(OFDM) symbols or slots. Data transmissions in the region 204 may bescheduled or grant-free to provide additional flexibility for datatransmissions for different applications and devices. For example, amobile device may transmit data in the region 204 after receiving agrant from a base station. In another example, multiple mobile devicesmay contend for the region 204 using a contention-based scheme that isapplicable. Grant-free data transmissions may be beneficial forsupporting communications for particular devices or applications in awireless network, such as, but not limited to, machine typecommunication (MTC). MTC may occur as part of the “Internet of things”,where a low data rate may be acceptable or mandated by the use of lesscomplex or costly data transmitters, receivers and power sources. Wherea communication from a machine to a network includes a status update,sensor reading, alarm or the like, the requirement for a high data rateis less likely. Such transmissions may include large numbers ofcommunications of relatively small packet size and require a relativelylow data rate. Similar characteristics may occur for downlinktransmissions from the network to the device or machine. Schedulingthese types of transmissions may be inefficient due to signalingoverhead incurred for small packet transmissions, the latency of ascheduling request and grant procedure, and the power consumptionincurred by a transmitting device or access point to handle thisoverhead and delay. The region 203 is a guard period (GP) separating thedownlink transmissions in the regions 201-202 and the uplinktransmissions in the regions 204-205. The GP 203 can help reduceinterference when switching between uplink and downlink transmissions inthe TDD network. The region 206 is a guard period, which separatesdownlink transmissions in the regions 201-202 from the preceding uplinktransmissions. It should be understood that no guard period is requiredbefore a downlink transmission that is not preceded by an uplinktransmission.

It is contemplated that the region 201 could alternatively oradditionally include pilot signals or reference signals. It is furthercontemplated that the region 201 could be used to transmit a controlsignal indicating whether the TDD TTI 200 is an uplink TTI or a downlinkTTI.

FIG. 2B is an embodiment downlink TTI 250 in a time division duplex(TDD) communications network. The TDD TTI 250 includes regions foruplink transmissions. As shown, the downlink TDD TTI 250 includesregions 251-256 divided in the time domain. The region 251 is allocatedfor downlink channels. The region 251 may be used, for example, to sendcontrol signals such as scheduling information for uplink datatransmissions, pilot signals or reference signals. The region 251 mayalso be used for downlink data transmissions, which may be scheduled orgrant-free transmissions. The downlink control signals and datatransmissions may each use contiguous time-frequency resources withinthe region 251, or may be interspersed within the region 251 in anysuitable manner. In particular, the control signals in region 251 andthe data signals in region 251 are not necessarily divided in the timedomain. The region 254 is allocated for uplink data transmissions, andfor transmission of uplink feedback information, such as measurementinformation (e.g. channel quality feedback, sounding reference signal),an uplink ACK/NACK message acknowledging receipt of a previous downlinkdata transmission. For example, the uplink ACK/NACK message iscommunicated to acknowledge receipt of a downlink data transmissioncommunicated in a previous downlink TDD TTI or in the region 251 of thedownlink TDD TTI 250. The uplink data transmissions and uplink feedbackinformation may each use contiguous time-frequency resources within theregion 254, or may be interspersed within the region 254 in any suitablemanner. In particular, the uplink data transmissions in region 254 andthe uplink feedback information in region 254 are not necessarilydivided in the time domain. As used herein, the region 254 is referredto as an opposite data and feedback region of TDD TTI 250.

In the example shown in FIG. 2B, the region 254 may be viewed as anuplink transmission opportunity (TO) for uplink transmissions of, e.g.,low latency uplink traffic or ACK/NACK messages, and may contain one ormore orthogonal frequency division multiplexing (OFDM) symbols or slots.Data transmissions in the region 254 may be scheduled or grant-free toprovide additional flexibility for data transmissions for differentapplications and devices. For example, a mobile device may transmit datain the region 254 after receiving a grant from a base station. Inanother example, multiple mobile devices may contend for the region 254using a contention-based scheme that is applicable. Grant-free datatransmissions may be beneficial for supporting communications forparticular devices or applications in a wireless network, such as, butnot limited to, machine type communication (MTC). MTC may occur as partof the “Internet of things”, where a low data rate may be acceptable ormandated by the use of less complex or costly data transmitters,receivers and power sources. Where a communication from a machine to anetwork includes a status update, sensor reading, alarm or the like, therequirement for a high data rate is less likely. Such transmissions mayinclude large numbers of communications of relatively small packet sizeand require a relatively low data rate. Similar characteristics mayoccur for downlink transmissions from the network to the device ormachine. Scheduling these types of transmissions may be inefficient dueto signaling overhead incurred for small packet transmissions, thelatency of a scheduling request and grant procedure, and the powerconsumption incurred by a transmitting device or access point to handlethis overhead and delay. The region 253 is a guard period (GP)separating the downlink transmissions in the region 251 and the uplinktransmissions in the region 254. The GP 253 can help reduce interferencewhen switching between uplink and downlink transmissions in the TDDnetwork. The region 256 is a guard period, which separates downlinktransmissions in the region 251 from the preceding uplink transmissions.It should be understood that no guard period is required before adownlink transmission that is not preceded by an uplink transmission.

FIG. 3A is an embodiment uplink TTI 300 in a TDD communications network.The uplink TTI 300 includes regions for downlink transmissions. Asshown, the uplink TTI 300 includes a region 301 for uplink controlchannels, a region 302 for uplink data transmissions, a region 303 as aguard period, a region 304 for downlink data transmissions, a region 305for transmission of a downlink ACK/NACK message acknowledging receipt ofa previous uplink data transmission, and a region 306 as another guardperiod. Similar to the downlink TDD TTI 200 in FIG. 2A, the regions301-305 are divided in the time domain.

FIG. 3B is an embodiment uplink TTI 310 in a TDD communications network.The uplink TTI 310 includes regions for downlink transmissions. Asshown, the uplink TTI 310 includes a region 311 for uplink controlsignals and uplink data transmissions, a region 313 as a guard period, aregion 314 for downlink data transmissions and transmission of adownlink ACK/NACK message acknowledging receipt of a previous uplinkdata transmission, and a region 316 as another guard period. Within theregion 311, the uplink control signals and uplink data transmissions mayeach use contiguous time-frequency resources, or may be interspersed inany suitable manner. In particular, the uplink control signals in region311 and the uplink data transmissions in region 311 are not necessarilydivided in the time domain. Similarly, within the region 314, thedownlink data transmissions and downlink ACK/NACK messages may each usecontiguous time-frequency resources, or may be interspersed in anysuitable manner. In particular, the downlink data transmissions inregion 314 and the downlink ACK/NACK messages in region 314 are notnecessarily divided in the time domain. Similar to the downlink TDD TTI250 in FIG. 2B, the regions 311-316 are divided in the time domain.

FIG. 3C is an embodiment uplink TTI 320 in a TDD communications network.The uplink TTI 320 includes regions for downlink transmissions. In thisembodiment, the downlink transmissions occur before the uplinktransmissions. As shown, the uplink TTI 320 includes a region 321 foruplink control channels including ACK/NACK messages acknowledgingreceipt of previous downlink transmissions, a region 322 for uplink datatransmissions, a region 323 as a guard period, a region 324 for downlinkcontrol signals, a region 325 for transmission of downlink data, and aregion 326 as another guard period. The control signals in region 324may include, for example, ACK/NACK messages acknowledging receipt of aprevious uplink transmission, or signaling indicating a grant of uplinkresources for the region 322. Similar to the downlink TDD TTI 200 inFIG. 2A, the regions 321-326 are divided in the time domain.

It is contemplated that the region 324 could be used to transmit acontrol signal indicating whether the TDD TTI 320 is an uplink TTI or adownlink TTI.

FIG. 3D is an embodiment uplink TTI 330 in a TDD communications network.The uplink TTI 330 includes regions for downlink transmissions. In thisembodiment, the downlink transmissions occur before the uplinktransmissions. As shown, the uplink TTI 330 includes a region 331 foruplink control signals and uplink data transmissions, a region 333 as aguard period, a region 334 for downlink data transmissions andtransmission of downlink control signals, and a region 336 as anotherguard period. The control signals in region 334 may include, forexample, ACK/NACK messages acknowledging receipt of a previous uplinktransmission, or signaling indicating a grant of uplink resources forthe region 331. Within the region 331, the uplink control signals anduplink data transmissions may each use contiguous time-frequencyresources, or may be interspersed in any suitable manner. In particular,the uplink control signals in region 331 and the uplink datatransmissions in region 331 are not necessarily divided in the timedomain. Similarly, within the region 334, the downlink datatransmissions and downlink control signals may each use contiguoustime-frequency resources, or may be interspersed in any suitable manner.In particular, the downlink data transmissions in region 334 and thedownlink control signals in region 334 are not necessarily divided inthe time domain. Similar to the downlink TDD TTI 200 in FIG. 2A, theregions 331-336 are divided in the time domain.

In the embodiments of FIGS. 2A, 2B, 3A, 3B, 3C and 3D, it should beunderstood that an ACK/NACK message can acknowledge the receipt of aprevious transmission in either the same TTI or an earlier TTI.

FIG. 4 is another embodiment downlink TTI 400 in a TDD communicationsnetwork. As shown, the downlink TTI 400 includes a region 401 fordownlink control channels, a region 402 for downlink data transmissions,a region 403 as a guard period, a region 404 for uplink datatransmissions, and a region 405 for transmission of uplink feedbackinformation, such as an uplink ACK/NACK message. In this example, theregion 401 and the region 402 are divided in the frequency domain, i.e.,the control signals in the region 401 and data signals in the region 402are transmitted during a same time period within the downlink TTI 400but over different frequency resources assigned to the downlink TTI 400.For example, when the downlink TTI 400 is used to transmit signals overa frequency sub-band divided into multiple sub-carriers fortransmissions, the control signals may be transmitted over a firstsub-carrier of the frequency sub-band, and the data signals may betransmitted over the other sub-carriers of the frequency sub-band.Similarly, the region 404 and region 405 are also divided in thefrequency domain, which indicates that the uplink data transmissions andthe uplink ACK/NACK message are transmitted during a same time periodwithin the downlink TTI 400 but over different frequency resourcesassigned to the downlink TTI 400. Division of the regions 401 and 402 inthe frequency domain may be different from that of the regions 404 and405. For example, the downlink data transmissions in the region 402 andthe uplink data transmissions in the region 404 are communicated overdifferent frequency resources. The region 406 is a guard periodseparating downlink transmissions in the regions 401-402 from apreceding uplink transmission.

FIG. 5 is another embodiment uplink TTI 500 in a TDD communicationsnetwork. As shown, the uplink TTI 500 includes a region 501 for uplinkcontrol channels, a region 502 for uplink data transmissions, a region503 as a guard period, a region 504 for downlink data transmissions, anda region 505 for transmission of a downlink ACK/NACK message. Similar tothe downlink TTI 400 in FIG. 4, the regions 501 and 502 are divided inthe frequency domain, and the regions 504 and 505 are divided in thefrequency domain. Region 506 is a guard period separating uplinktransmissions in the regions 501-502 from a preceding downlinktransmission.

As used herein, the regions 204, 304, 404 and 504 are referred to asopposite data regions in a TDD TTI, and the regions 205, 305, 405 and505 are referred to as opposite feedback regions (or opposite ACK/NACKregions) in a TDD TTI, because transmissions in these regions are in adirection opposite to the transmission direction of the TDD TTI. Theseregions are also generally referred to as opposite regions in a TDD TTI.The TDD TTIs with TTI structures as illustrated in FIGS. 2-5 are merelyfor illustrative purposes, and should not be interpreted to be limitingto the scope of the claims. One of ordinary skill in the art wouldrecognize that there are many different mechanisms or schemes toimplement data and/or feedback information communication in a TDD TTIand opposite regions in the TDD TTI.

In some embodiments, transmissions in one or more opposite regions of aTDD TTI are configurable. In one embodiment, a TDD TTI of onetransmission direction, i.e., downlink or uplink, may include differentconfigurations of an opposite data region and an opposite feedbackregion, both of which are used for transmissions in an oppositedirection of the TDD TTI, i.e., uplink or downlink. In one embodiment, adownlink TDD TTI may not contain any opposite data region or oppositefeedback region. In another embodiment, the downlink TDD TTI may containmore than one opposite data region or opposite feedback region. In yetanother embodiment, TDD TTIs include opposite regions at differentlocations and with different lengths. The number, lengths and locationsof the opposite regions may vary depending on factors such as traffictypes, traffic latency requirements, traffic sizes, network load, aswell as frame structure configurations. The different configurations ofan opposite data region and an opposite feedback region in a TDD TTIherein are referred to as TTI switching types (or switching types),because including these opposite regions in the TDD TTI requires atransceiver to switch between a transmitting mode and a receiving mode.Each switching type is characterized by its configuration information,which may include the number of opposite data regions, the number ofopposite feedback regions, location and duration of each of theseopposite regions, and frequency resources for transmissions in theseopposite regions. A switching type may indicate there is zero, one ormore opposite regions in a TDD TTI.

In some embodiments, a switching type of a TDD TTI is pre-defined ordefined when needed, and configuration information about the switchingtype for the TDD TTI is signaled for communication. The signaling may betransmitted in a control channel via broadcast, multi-cast, or unicast.For example, when there is no data for traffic types which require aconsistent low latency feedback, UEs may be signaled to disable oppositefeedback regions in TDD TTIs. In another example, a base station isaware of a need for one or more opposite regions in a TDD TTI,determines a switching type for the TDD TTI, and transmits suchconfiguration information of the TDD TTI to a UE. In yet anotherexample, a switching type may also be determined for a TDD TTI inresponse to a request from a UE. In another embodiment, each switchingtype corresponding to a frame structure configuration is pre-defined,indexed, and made known to all UEs. In this example, an indexcorresponding to a switching type configured for a TDD TTI may betransmitted, by which a UE identifies the switching type it may use. Oneof ordinary skill in the art would recognize many variations andalternatives for signaling configuration information of TDD TTIsregarding switching types.

As mentioned above, different frame structure configurations correspondto different combinations of frame parameters. Using different framestructure configurations to communicate traffic may provide significantspectrum flexibility, because using different combinations of SCspacings, TTI lengths, CP lengths, and symbol durations may realizeperformance advantages in, e.g., latency and spectral efficiency. Aframe structure configuration corresponding to a set of frame parametersmay be assigned to a TDD TTI in accordance with traffic types, number ofUEs being served by a base station, latency requirements, or a specificrequest from a UE. A switching type may also be selected for the TDD TTIin accordance with the assigned frame structure configuration, a latencyrequirement, or a UE's request. FIG. 6 is a diagram of embodiment TTDTTIs 600 configured to have different frame structure configurations andswitching types for wireless communications. In this example, each framestructure configuration corresponds to a different set of SC spacing, CPlength and TTI length. As shown, frame structure configuration 1 isassigned to TDD TTIs 612, 614 and 616; frame structure configuration 2is assigned to TDD TTIs 622, 624 and 626; and frame structureconfiguration 3 is assigned to TDD TTIs 632, 634 and 636.

In some embodiments, each TDD TTI has a switching type corresponding toits assigned frame structure configuration. As described above, aswitching type indicates a configuration of an opposite data region andan opposite feedback region in a TTI for transmitting data and ACK/NACKmessages in an opposite direction of the TTI's transmission direction.Different switching types may be defined corresponding to differentframe structure configurations. In this example as illustrated in FIG.6, each of the three frame structure configurations corresponds to threeswitching types, namely, Type 0, Type 1 and Type 2. In each of the threeframe structure configurations, there is no opposite region within a TDDTTI of Type 0. Type 1 and Type 2 indicate different combinations ofopposite data and feedback regions. As shown, TDD TTI 612 is a Type 0TTI. TDD TTI 614 is a Type 1 TTI, and includes an opposite feedbackregion 651 at the end of the TTI. TDD TTI 616 is a Type 2 TTIcorresponding to the frame structure configuration 1, and includes anopposite data region 652 and an opposite feedback region 653 at the end.The two opposite regions 652 and 653 are adjacent to each other in thetime domain, and are herein referred to as a pair of opposite regions. ATDD TTI of this type, e.g., TDD TTI 616, may be considered to beself-contained because downlink and uplink data, control and feedbackinformation exist in this TTI.

FIG. 6 also shows that TDD TTI 622 is also a Type 0 TTI. TDD TTI 624 isa Type 1 TTI including an opposite data region 661 and an oppositefeedback region 662 at the end. TDD TTI 626 is a Type 2 TTIcorresponding to the frame structure configuration 2, and includes twopairs of opposite regions. As shown, one pair of opposite regions 663and 664 is included in the middle of the TDD TTI 626, and another pairof opposite regions 665 and 666 is included at the end of the TDD TTI626. TDD TTI 632 is a Type 0 TTI. TDD TTI 634 is a Type 1 TTIcorresponding to the frame structure configuration 3, and TDD TTI 636 isa Type 2 TTI corresponding to the frame structure configuration 3. FIG.6 illustrates that adjacent opposite data region and opposite feedbackregion are arranged in a time multiplexed fashion, these regions mayalso be in a frequency multiplexed fashion.

In some embodiments, different frame structure configurations may havedifferent sets of switching types defined. For example, long TTIs, e.g.TTIs of 1 ms or 5 ms, may have more switching types defined than thosewith short TTI lengths, e.g. 0.1 ms or 0.125 ms, to provide more optionsfor data and feedback information transmissions in an oppositedirection. In some embodiments, locations of opposite regions fordifferent switching types may be pre-defined. For example, for switchingtypes with one opposite region, the opposite region may be defined tooccur at the end of a TDD TTI or in the middle of the TDD TTI. Inanother example, for switching types with two opposite regions, oneopposite region may be defined to occur at the end of a TDD TTI and theother may be defined to occur in the middle of the TDD TTI. One ofordinary skill in the art would recognize many variations for definingdifferent switching types corresponding to different frame structureconfigurations and arranging opposite regions within a TDD TTI. It willbe appreciated that for switching types with an opposite data region andan opposite feedback region, the two regions may be located at adjacenttime periods within a TDD TTI, or at the same time period but overdifferent frequency resources, to reduce the number of downlink anduplink transitions, and thus the number of guard periods. As well,although the embodiments of the present disclosure illustrate TDD TTIswith an opposite data region followed by an opposite feedback region, itwill be appreciated that these regions may be defined in any order. Oneof ordinary skill in the art would also recognize that, although notillustrated in FIG. 6, a guard period would be included in a TDD TTI atany transition between downlink and uplink transmissions.

FIGS. 7-8 illustrate tables 700 and 800 for representing frame structureconfigurations and their corresponding switching types according toembodiments of the present disclosure. In one embodiment, one table isdefined for each frame structure configuration, representing a set ofcorresponding switching types. As shown in FIG. 7, a table 710 is usedto represent four switching types defined corresponding to framestructure configuration 1. Table 720 and table 730 include seven andfour switching types corresponding to frame structure configuration 2and frame structure configuration 3, respectively. As can be seen fromFIG. 7, different frame structure configurations may have different setsof switching types defined. For example, each of the three framestructure configurations has a Type 2 switching type, which, however,may be defined differently from each other. In another embodiment, onetable is used to represent switching types for multiple frame structureconfigurations. As shown in FIG. 8, table 800 includes seven switchingtypes defined consistently for all three frame structure configurations1-3. Whether a frame structure configuration has a switching typedefined is shown by a mark in the corresponding cell of the table 800,e.g., checked or marked as “not available” (N/A). One of ordinary skillin the art would recognize many variations and alternatives forrepresenting different frame structure configurations and correspondingswitching types.

In some embodiments, a TDD frame may carry OFDM or filtered OFDM(f-OFDM) signals communicated in TTIs in accordance with different framestructure configurations and switching types. An f-OFDM signal may begenerated by applying a pulse shaping digital filter to an OFDM signal.TTIs may be assigned different frame structure configurations withdifferent switching types for communications over different OFDMfrequency sub-bands. A network controller may be used to assign framestructure configurations to the TTIs over different frequency sub-bandsand select switching types for the TTIs. The network controller may sendan indication to a base station, indicating that the base stationcommunicates OFDM signals in the TTIs in accordance with the assignedframe structure configurations and selected switching types. The basestation may also signal the frame structure configurations and switchingtypes to UEs for communications in the TTIs.

FIG. 9 is a diagram of an embodiment TDD frame 900, where TTIs ofdifferent lengths are used to communicate OFDM signals. As shown, TTIs912, 914, 916 and 918 are assigned to a frequency sub-band 910, and havea TTI length of T1. TTIs, such as TTI 932, assigned to a sub-band 930have a TTI length of T2. TTIs assigned to a sub-band 950 have a TTIlength of T3. The lengths of TTIs may be integer multiples of apre-defined minimum TTI length. For example, when a pre-defined minimumTTI length is 0.1 ms, the T1 may be 0.2 ms, T2 may be 0.5 ms, and T3 maybe 1 ms. As another example, when a pre-defined minimum TTI length is0.125 ms, T1 may be 0.25 ms, T2 may be 0.5 ms, and T3 may be 1 ms. TheTDD frame 900 is divided into slots in the time domain, such as theslots k, k+1 and k+2. As shown, a TTI in the sub-band 930 spans oneslot, and a TTI in the sub-band 950 spans two slots. In one embodiment,the bandwidth of a frequency sub-band may change over time. For example,bandwidths of the sub-band 910 are different during the slot k and slotk+1. Similarly, bandwidths of the sub-band 930 are different during theslot k and slot k+1. For simplicity of description, each TTI in the TDDframe 900 of this example is a downlink TTI for downlink transmissions,and may include a portion for communicating downlink control informationand a portion for communicating data. One of ordinary skill in the artwould recognize that the TDD frame 900 may include TTIs for downlinktransmissions, uplink transmissions, or both.

In some embodiments, one or more configurable time intervals for uplinktransmissions may be included in the TDD frame 900 to accommodatedifferent uplink transmission requirements, such as low latencyrequirements. These configurable time intervals may also providedynamics for flexible resource allocation and spectrum utilization foruplink transmissions. As shown in FIG. 900, the TDD frame 900 includesconfigurable time intervals 921, 923, 925, 941, 943, 945, 961, 963 and965 at the end of each slot over frequency sub-bands 910, 930 and 950,which are aligned across the frequency sub-bands in the time domain. Theconfigurable time intervals 921, 923 and 925 are uplink TTIs. Theconfigurable time intervals 941, 943, 945, 961, 963 and 965 may beopposite data and/or feedback regions within TDD TTIs, as describedabove with respect to FIGS. 2-3. Specifically, the configurable timeinterval 961 splits a TTI in the sub-band 950 into two time intervals952 and 954. Locations and duration of the configurable time intervalsmay be pre-defined. In one embodiment, the lengths of the configurabletime intervals may be integer multiples of a length of a pre-definedminimum TTI, so that these configurable time intervals may be alignedacross the sub-bands in the time domain. These configurable timeintervals may be used for communicating uplink data or uplink feedbackinformation, such as uplink ACK/NACK messages. For example, theconfigurable time interval 921 in the sub-band 910 may be used totransmit an uplink ACK/NACK message corresponding to the datatransmitted in the TTI 912. Retransmission of the data may be performedin a later TTI, e.g., the TTI 916 in the sub-band 910. The uplinkACK/NACK message corresponding to the data transmitted in the TTI 912may also be transmitted in the configurable time interval 961 in thesub-band 950. In another example, an uplink ACK/NACK messagecorresponding to data communicated in the TTI 914 may be transmitted inthe configurable time interval 923 in the sub-band 910. The datacommunicated in the TTI 914 may be retransmitted in the TTI 918 in thesub-band 910. The configurable time interval 963 in the sub-band 950 mayalso be used to transmit the uplink ACK/NACK message corresponding tothe data communicated in the TTI 914. A configurable time interval inone sub-band may be used to transmit an uplink ACK/NACK messagecorresponding to a downlink data transmitted in a downlink TTI in anysub-band of the TDD frame 900. The configurable time intervals in thisexample may be used to reduce HARQ round trip time (RTT) delays. Asdescribed above, a GP (not shown) is included whenever there istransition between a downlink transmission and an uplink transmission.GPs are aligned across all frequency sub-bands in the time domain.

FIG. 10 is a diagram of another embodiment TDD frame 1000, which carriesf-OFDM signals communicated in TTIs over different frequency sub-bands.FIG. 10 illustrates three frequency sub-bands 1010, 1020 and 1030. EachTTI may be a downlink or an uplink TTI. In one embodiment, a pattern ofdownlink and uplink TTIs of a frame, which may be referred to as adownlink/uplink TTI configuration, may be pre-defined for the TDD frame1000. A downlink/uplink TTI configuration specifies a downlink:uplinkTTI traffic ratio. The downlink:uplink TTI traffic ratio may bedetermined based on traffic types, number of UEs served in a network,latency requirements, etc. In this example, the downlink:uplink TTIratio is 1:1. In one embodiment, TTIs in different frequency sub-bandsmay have different lengths. In this example, TTIs in sub-band 1010 havea TTI length of 0.125 ms, such as downlink TTI 1012 and uplink TTI 1014.TTIs in sub-band 1020 have a TTI length of 0.25 ms, such as downlink TTI1022 and uplink TTI 1024. TTIs in sub-band 1030 have a TTI length of 1ms, such as downlink TTI 1031. As shown, the downlink TTI 1031 insub-band 1030 is split into four regions 1032, 1034, 1036 and 1038 bythe insertion of uplink TTIs 1041, 1043 and 1045. Each of the fourregions 1032, 1034, 1036 and 1038 has a duration of 0.25 ms. The uplinkTTIs 1041, 1043 and 1045 inserted in the downlink TTI may be used forcommunicating data or ACK/NACK feedback messages to meet latencyrequirements. Although the downlink TTI is split into four regions 1032,1034, 1036 and 1038, the four regions are not separate TTIs with theirown control, data and pilot channels; instead, they share the controland pilots channels, and transmission and receiving processing of thefour regions are performed over the entire TTI length, i.e., 1 ms. GPs,e.g., OFDM symbols, are inserted (not shown) to facilitate switchingbetween downlink and uplink transmissions, and are aligned in the timedomain across all the frequency sub-bands. FIG. 10 illustrates that noTTI includes any opposite feedback or data regions as illustrated abovein FIGS. 2-5.

FIG. 11 is a diagram of another embodiment TDD frame 1100, which carriesf-OFDM signals communicated in TTIs over different frequency sub-bands1110, 1120 and 1130. The TDD frame 1100 has a downlink:uplink TTI ratioof 6:2. TTIs in different frequency sub-bands in this example also havedifferent lengths. TTIs in frequency sub-band 1110 have a TTI length of0.125 ms. TTIs in frequency sub-band 1120 have a TTI length of 0.25 ms.TTIs in frequency sub-band 1130 have a TTI length of 0.5 ms. Regions1132 and 1134, split by an uplink TTI 1133, form one TTI in frequencysub-band 1130. In one embodiment, the TDD frame 1100 may include TTIs ofdifferent switching types. For example, TTIs 1112 and 1114 in frequencysub-band 1110 include one opposite feedback region at the end of eachcorresponding TTI. TTIs 1116 and 1118 include a pair of opposite regionsat the end of each corresponding TTI. TTIs 1122 and 1124 in frequencysub-band 1120 include one opposite feedback region located in the middleand one opposite feedback region at the end of each corresponding TTI.TTIs 1126 and 1128 include one opposite feedback region in the middleand a pair of opposite regions at the end. TTIs 1136 and 1138 infrequency sub-band 1130 include four opposite feedback regions and oneopposite data region within a corresponding TTI. The TTI formed byregions 1132 and 1134 includes four opposite feedback regions. UplinkTTI 1133 includes one opposite feedback region located in the middle andanother opposite feedback region located at the end. GPs are inserted(not shown) whenever there is switching between downlink and uplinktransmissions, and are aligned in the time domain across multiplefrequency sub-bands. Consequently, the opposite feedback regions and theopposite data regions in TTIs of the TDD frame 1100 are also alignedacross the frequency sub-bands in the time domain. Although FIG. 11illustrates that a pair of opposite regions in a TTI, such as TTI 1126,are arranged to be adjacent to each other in the time domain, the pairof opposite regions may alternatively be assigned to different frequencyresources during the same time period.

It should be understood that, although opposite direction regions ofTTIs are shown as being aligned in the time domain across multiplefrequency sub-bands, the opposite direction regions may be used fordifferent types of transmission in different sub-bands. For example, theopposite direction regions of multiple sub-bands that are aligned in thetime domain can be used for ACK/NACK feedback in a first sub-band, datatransmissions in a second sub-band, and sounding reference signals (SRS)in a third sub-band.

It is further contemplated that, in an alternative embodiment, only theregions corresponding to control signaling may be aligned in the samedirection across multiple sub-bands, and the regions corresponding touplink or downlink data may not necessarily all be aligned in the samedirection. In such an embodiment, control signaling would not be subjectto interference from opposite-direction control signaling in nearbysub-bands, and data transmissions could be subject to other techniquesto mitigate or tolerate interference due to opposite-direction datacommunication in nearby sub-bands.

FIG. 12 is a diagram of another embodiment TDD frame 1200, which carriesf-OFDM signals communicated in TTIs over different frequency sub-bands1210 and 1220. The TDD frame 1200 has a downlink:uplink TTI ratio of6:2. TTIs in frequency sub-band 1210 have a TTI length 0.25 ms, and TTIsin frequency sub-band 1220 have a TTI length 0.5 ms. Regions 1223 and1224, split by an uplink TTI 1225, form one TTI in frequency sub-band1220. FIG. 12 also illustrates that TTIs in the TDD frame 1200 may havedifferent switching types. For example, TTIs 1212 and 1216 have oneopposite feedback region at the end of each corresponding TTI, TTI 1214has a pair of opposite regions located at the end, and TTI 1218 has oneopposite data region at the end. In another example, TTI 1222 containsone opposite feedback region in the middle and a pair of oppositeregions at the end, the TTI formed by the regions 1223 and 1224 containstwo opposite feedback regions located in the middle and at the end ofthe TTI, TTI 1225 has one opposite feedback region at the end, and TTI1226 has one opposite data region in the middle and one oppositefeedback region at the end. In one embodiment, durations of the oppositedata regions or opposite feedback regions may be different for differentTTIs or within the same TTI. For example, the opposite data regions inTTIs 1214 and 1218 have different durations, the opposite feedbackregions in TTIs 1212 and 1214 have different durations, and the oppositefeedback regions in regions 1223 and 1224, which form one TTI, also havedifferent durations. Similarly, GPs are inserted (not shown) wheneverthere is switching between downlink and uplink transmissions, and arealigned in the time domain across all the frequency sub-bands.

FIG. 13 illustrates a diagram of a TDD frame 1300, where f-OFDM signalsare communicated in TTIs over different frequency sub-bands withdifferent subcarrier spacings. TDD frame 1300 shows frequency sub-bands1310 and 1320 with subcarrier spacings of 30 kHz and 60 kHz. The TDDframe 1300 has a downlink:uplink TTI ratio of 6:2, and TTIs in differentf-OFDM frequency sub-bands have different TTI lengths. For example, TTIsin frequency sub-band 1310 have a length of 0.125 ms, and TTIs infrequency sub-band 1320 have a length of 0.25 ms. TTIs in the TDD frame1300 may also have different switching types. For example, TTIs 1312 and1322 have a pair of opposite regions at the end, TTI 1314 does not haveany opposite region, and TTIs 1316, 1324 and 1326 have one oppositefeedback region at the end.

FIG. 14 illustrates a diagram of another TDD frame 1400, where f-OFDMsignals are communicated in TTIs over different frequency sub-bands withdifferent subcarrier spacings. The TDD frame 1400 shows frequencysub-bands 1410 and 1420 with subcarrier spacings of 15 kHz and 30 kHz,and the TDD frame 1400 has a downlink:uplink TTI ratio of 6:2. TTIs inthe TDD frame 1400 include TTIs having different lengths and differentswitching types. TTIs in frequency sub-band 1410 have a length of 0.25ms, and TTIs in frequency sub-bands 1420 have a length of 0.5 ms. TTIs1412 and 1422 have a pair of opposite regions at the end. TTI 1414 doesnot have any opposite region. TTIs 1416 and 1424 have on oppositefeedback region at the end. As shown, opposite feedback regions andopposite data regions included in TTIs are aligned across the frequencysub-bands in the time domain. Similarly, GPs are inserted (not shown)whenever there is switching between downlink and uplink transmissions,and are aligned in the time domain across all the frequency sub-bands.One of ordinary skill in the art would recognize many variations andmodifications for communicating OFDM signals in TDD frames in accordancewith different frame structure configurations and switching type, whereTTIs, opposite data regions and opposite feedback regions may bearranged differently than what are illustrated in FIGS. 9-14.

As described above, different TTIs in a TDD frame may be assigned todifferent frame structure configurations and have different switchingtypes. GPs may be included wherever there is a transition betweendownlink and uplink transmissions. The GPs included in the TDD frameneed to be aligned in the time domain across different frequencysub-bands in order to prevent or reduce interference. In someembodiments, the alignment of GPs may be provided by virtue of framestructure configurations having symbol durations that are integermultiples of each other. In some embodiments, alignment of GPs may alsobe implemented using special OFDM symbols having different durationsthan that specified by frame structure configurations. In one example,this may be implemented by varying the CP lengths of the special OFDMsymbols. FIG. 15 is a diagram of a TDD frame 1500 where special OFDMsymbols are used to align GPs across frequency sub-bands. Details ofTTIs and opposite feedback and data regions within each TTI are notshown, but it can be appreciated that with different combinations ofthese portions and different signal transmissions, the end of signaltransmissions in TTIs of each frequency sub-band may not be aligned inthe time domain. The TDD frame 1500 carries f-OFDM signals communicatedover two different frequency sub-bands 1510 and 1520 with differentframe structure configurations. As described above, different framestructure configurations specify different sets of frame parameters,including bandwidth, TTI length, OFDM symbol duration, CP length, etc.In this example, OFDM symbol duration (including CP) in the frequencysub-band 1510 is T1, and OFDM symbol duration (including CP) in thefrequency sub-band 1520 is T2. FIG. 15 illustrates a region 1519 in thefrequency sub-band 1510 which may include multiple OFDM symbols (notshown) with a symbol duration of T1, and OFDM symbols 1512, 1514 and1518 in the frequency sub-band 1510 with a symbol duration of T1. FIG.15 also illustrates a region 1531 in the frequency sub-band 1520 whichmay include multiple OFDM symbols (not shown) with a symbol duration ofT2, and OFDM symbols 1522, 1524 and 1532 in the frequency sub-band 1520with a duration of T2. GPs 1516 and 1526 are inserted to separatedownlink and uplink transmissions. In one embodiment, special OFDMsymbols 1528 and 1530 having different durations than T2 are placedbefore and after the GP 1526 in order to align the GP 1526 with the GP1516. The special OFDM symbols 1528 and 1530 may also have differentsymbol durations than each other, e.g., by having different CP lengths.Depending on symbol durations of different frame structureconfigurations, one or more special OFDM symbols may be placed before,after, or before and after one or more GPs so that GPs are alignedacross frequency sub-bands in the time domain.

In some embodiments, TTIs assigned to the same frequency resource may beassigned different frame structure configurations and switching types.FIG. 16 is a diagram of an embodiment TDD frame 1600 including TTIs ofdifferent frame structure configurations and switching types. TTIs 1602,1604 and 1606 are assigned the same frame structure configuration, withthe same TTI length of T1. These TTIs do not contain any oppositeACK/NACK or data region. TTI 1612 is used to communicate signals at alater time than the TTIs 1602, 1604 and 1606. As shown, TTI 1612 isassigned a different frame structure configuration, with a TTI length ofT2 and containing two pair of opposite regions. In one embodiment,information about a frame structure configuration and a switching typedefined for one or more TTIs may be broadcast by a wireless networkbefore transmissions in such TTIs begin. FIG. 16 shows two differentframe structure configurations merely for illustrative purpose. One ofordinary skill in the art would recognize many variations andmodifications to use different frame structure configurations andswitching types for communications in TTIs over the same frequencyresource.

As described above, TTIs may be configured to have different framestructure configurations and TTI switching types, and used tocommunicate signals over different frequency sub-bands. Configurationinformation of a TTI may be pre-defined or defined dynamically, andsignaled to UEs. The configuration information of a TTI may include oneor more of frame structure configurations, and TTI switching types,frequency sub-bands, and downlink/uplink TTI configuration, etc.Depending on the flexibility and types and configurations of frames usedin a wireless network, it will be appreciated that different schemes maybe defined to limit the number of bits required to signal suchconfiguration information. The signaling may be transmitted throughbroadcast, multicast or unicast semi-statically or statically. In oneembodiment, the configuration information is broadcast semi-staticallyto UEs. In another embodiment, the configuration information istransmitted to target UEs. In another embodiment, the configurationinformation may be signaled through a control channel with othersignaling overhead messages. Depending on the types of devices andtraffic being supported in a wireless network and also the load in thewireless network, TDD frames may be adaptively configured to flexiblyaccommodate data transmissions in TTIs using different frame structureconfigurations, switching types, and frequency sub-bands. Thedetermination of how downlink and uplink transmissions are communicatedin TTIs may be performed by a base station or another node or entity ina wireless network, such as a scheduling entity or a central controllerassociated with multiple base stations.

FIG. 17 is a flowchart of an embodiment method 1700 for wirelesscommunications. At step 1702, a device communicates a first datatransmission in a first TDD TTI of a radio frame in a first direction,and at step 1704, the device communicates a second data transmission inthe first TDD TTI in a second direction. One of the first direction andthe second direction may be a transmit direction, and the other of thefirst direction and the second direction may be a receive direction. Inone embodiment, the first direction is an uplink direction and thesecond direction is a downlink direction, or vice versa. The first TDDTTI may be configured with a first frame structure configuration. Thefirst TDD TTI may include a GP separating the first and the second datatransmission. In one embodiment, the first data transmission and thesecond data transmission are communicated over different frequencyresources. In another embodiment, the first data transmission and thesecond data transmission are communicated over the same frequencysub-band. The first data transmission or the second data transmissionmay also be communicated grant-free. For example, the first datatransmission or the second data transmission is communicated inaccordance with a contention-based mechanism. The device may be a basestation or a user equipment. The device may further signal, to a userequipment, at least the first frame structure configuration orconfiguration information of the first TDD TTI.

In some embodiments, the first TDD TTI is a downlink TTI including anuplink transmission opportunity. The uplink transmission opportunity maybe viewed as an opposite data region in the downlink TTI. The downlinkTTI may carry control information specifying a location, a duration, ora frequency resource of the uplink transmission opportunity in thedownlink TTI. The location, a duration, or a frequency resource of theuplink transmission opportunity may be pre-defined and defined whenneeded. In one embodiment, the device may further communicate an uplinkACK/NAK message, which confirms whether a previous downlink datatransmission communicated was successfully received. The ACK/NAK messagemay be communicated with an uplink data transmission over differentfrequency resources during the same time period or over the samefrequency resources during different time periods. The uplink datatransmission may be one of the first data transmission or the seconddata transmission.

In some embodiments, the first TDD TTI is an uplink TTI including adownlink transmission opportunity. The uplink TTI may carry controlinformation specifying a location, a duration, or a frequency resourceof the downlink transmission opportunity in the uplink TTI. The downlinktransmission opportunity may be viewed as an opposite data region in theuplink TTI. The location, a duration, or a frequency resource of thedownlink transmission opportunity may be pre-defined and defined whenneeded. In one embodiment, the device may further communicate a downlinkACK/NAK message, which confirms whether a previous uplink datatransmission communicated was successfully received. The ACK/NAK messagemay be communicated with a downlink data transmission over differentfrequency resources during the same time period or over the samefrequency resources during different time periods. The downlink datatransmission may be one of the first data transmission or the seconddata transmission.

In one embodiment, the device may further communicate a third datatransmission in a second TDD TTI of the radio frame, where the TDD TTIis configured with a second frame structure configuration different thanthe first frame structure configuration. The third data transmission maybe communicated in a transmit direction or a receive direction. Thefirst TDD TTI and the second TDD TTI may be assigned to different OFDMfrequency sub-bands or the same OFDM frequency sub-band. In one example,the first TDD TTI and the second TDD TTI have different TTI lengths. Inanother example, the first and the second data transmissions in thefirst TDD TTI and the third data transmission in second TDD TTI arecommunicated in accordance with different subcarrier spacings, or OFDMsymbols of different lengths. In another embodiment, the device mayfurther communicate a fourth data transmission in the second TDD TTI.The third data transmission may be communicated in a transmit directionand the fourth data transmission may be communicated in a receivedirection, or vice versa. In one embodiment, the second TDD TTI may be adownlink TTI including an uplink transmission opportunity, or may be anuplink TTI including a downlink transmission opportunity. In yet anotherembodiment, the device may further communicate an ACK/NAK message in thesecond TDD TTI, where the third data transmission and the ACK/NAKmessage travel in opposite transmission directions than one another.

In some embodiments, a network controller may assign a first framestructure configuration for communicating in a first TDD TTI in a firstdirection over a first frequency sub-band. The first frame structureconfiguration corresponds to a first set of frame parameters. The firstset of frame parameters comprises a subcarrier spacing, a TTI length, anOFDM symbol duration, or a cyclic prefix length. The network controllermay be located at a base station, a higher layer network node, or anyother applicable network element in a wireless network. The networkcontroller may also select a switching type for the first TDD TTI. Theswitching type indicates whether or not the first TDD TTI includes atleast one transmission opportunity for communicating in a seconddirection. One of the first direction and the second direction may be atransmit direction, and the other of the first direction and the seconddirection may be a receive direction. The network controller may thensend an indication, e.g., to a base station, indicating communication ofOFDM signals in the first TDD TTI in accordance with the first set offrame parameters and the selected switching type. The first framestructure configuration may be assigned in accordance with a traffictype of data communicated in the first TDD TTI, the number of userequipments being served by a base station, a latency requirement, or arequest from a UE. The switching type may be selected in accordance withthe assigned first frame structure configuration, a latency requirement,or a request from a user equipment. The network controller may alsoassign a second frame structure configuration for communicating in asecond TDD TTI over a frequency sub-band that is same as or differentthan the first frequency sub-band. The second frame structureconfiguration corresponds to a second set of frame parameters differentthan the first set of frame parameters.

FIG. 18 is a block diagram of an embodiment processing system 1800 forperforming methods described herein, which may be installed in a hostdevice. As shown, the processing system 1800 includes a processor 1804,a memory 1806, and interfaces 1810-1814, which may (or may not) bearranged as shown in FIG. 18. The processor 1804 may be any component orcollection of components adapted to perform computations and/or otherprocessing related tasks, and the memory 1806 may be any component orcollection of components adapted to store programming and/orinstructions for execution by the processor 1804. In an embodiment, thememory 1806 includes a non-transitory computer readable medium. Theinterfaces 1810, 1812, 1814 may be any component or collection ofcomponents that allow the processing system 1800 to communicate withother devices/components and/or a user. For example, one or more of theinterfaces 1810, 1812, 1814 may be adapted to communicate data, control,or management messages from the processor 1804 to applications installedon the host device and/or a remote device. As another example, one ormore of the interfaces 1810, 1812, 1814 may be adapted to allow a useror user device (e.g., personal computer (PC), etc.) tointeract/communicate with the processing system 1800. The processingsystem 1800 may include additional components not depicted in FIG. 18,such as long term storage (e.g., non-volatile memory, etc.).

In some embodiments, the processing system 1800 is included in a networkdevice that is accessing, or part otherwise of, a telecommunicationsnetwork. In one example, the processing system 1800 is in a network-sidedevice in a wireless or wireline telecommunications network, such as abase station, a relay station, a scheduler, a controller, a gateway, arouter, an applications server, or any other device in thetelecommunications network. In other embodiments, the processing system1800 is in a user-side device accessing a wireless or wirelinetelecommunications network, such as a mobile station, a user equipment(UE), a personal computer (PC), a tablet, a wearable communicationsdevice (e.g., a smartwatch, etc.), or any other device adapted to accessa telecommunications network.

In some embodiments, one or more of the interfaces 1810, 1812, 1814connects the processing system 1800 to a transceiver adapted to transmitand receive signaling over the telecommunications network. FIG. 19 is ablock diagram of a transceiver 1900 adapted to transmit and receivesignaling over a telecommunications network. The transceiver 1900 may beinstalled in a host device. As shown, the transceiver 1900 comprises anetwork-side interface 1902, a coupler 1904, a transmitter 1906, areceiver 1908, a signal processor 1910, and device-side interface(s)1912. The network-side interface 1902 may include any component orcollection of components adapted to transmit or receive signaling over awireless or wireline telecommunications network. The coupler 1904 mayinclude any component or collection of components adapted to facilitatebi-directional communication over the network-side interface 1902. Thetransmitter 1906 may include any component or collection of components(e.g., up-converter, power amplifier, etc.) adapted to convert abaseband signal into a modulated carrier signal suitable fortransmission over the network-side interface 1902. The receiver 1908 mayinclude any component or collection of components (e.g., down-converter,low noise amplifier, etc.) adapted to convert a carrier signal receivedover the network-side interface 1902 into a baseband signal. The signalprocessor 1910 may include any component or collection of componentsadapted to convert a baseband signal into a data signal suitable forcommunication over the device-side interface(s) 1912, or vice-versa. Thedevice-side interface(s) 1912 may include any component or collection ofcomponents adapted to communicate data-signals between the signalprocessor 1910 and components within the host device (e.g., theprocessing system 1800, local area network (LAN) ports, etc.).

The transceiver 1900 may transmit and receive signaling over any type ofcommunications medium. In some embodiments, the transceiver 1900transmits and receives signaling over a wireless medium. For example,the transceiver 1900 may be a wireless transceiver adapted tocommunicate in accordance with a wireless telecommunications protocol,such as a cellular protocol (e.g., long-term evolution (LTE), etc.), awireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or anyother type of wireless protocol (e.g., Bluetooth, near fieldcommunication (NFC), etc.). In such embodiments, the network-sideinterface 1902 comprises one or more antenna/radiating elements. Forexample, the network-side interface 1902 may include a single antenna,multiple separate antennas, or a multi-antenna array configured formulti-layer communication, e.g., single input multiple output (SIMO),multiple input single output (MISO), multiple input multiple output(MIMO), etc. In other embodiments, the transceiver 1900 transmits andreceives signaling over a wireline medium, e.g., twisted-pair cable,coaxial cable, optical fiber, etc. Specific processing systems and/ortransceivers may utilize all of the components shown, or only a subsetof the components, and levels of integration may vary from device todevice.

Although the description has been described in detail, it should beunderstood that various changes, substitutions and alterations can bemade without departing from the spirit and scope of this disclosure asdefined by the appended claims. Moreover, the scope of the disclosure isnot intended to be limited to the particular embodiments describedherein, as one of ordinary skill in the art will readily appreciate fromthis disclosure that processes, machines, manufacture, compositions ofmatter, means, methods, or steps, presently existing or later to bedeveloped, may perform substantially the same function or achievesubstantially the same result as the corresponding embodiments describedherein. Accordingly, the appended claims are intended to include withintheir scope such processes, machines, manufacture, compositions ofmatter, means, methods, or steps.

What is claimed is:
 1. A method for wireless communications, comprising:communicating, by a device, a first data transmission in a first timedivision duplexing (TDD) scheduling interval in a first direction, thefirst TDD scheduling interval being configured with a first framestructure configuration; and communicating, by the device, a second datatransmission in the first TDD scheduling interval in a second direction,one of the first direction and the second direction being a transmitdirection, and the other of the first direction and the second directionbeing a receive direction.
 2. The method of claim 1, further comprisingsignaling, to a user equipment, at least the first frame structureconfiguration or configuration information of the first TDD schedulinginterval.
 3. The method of claim 1, wherein the first data transmissionand the second data transmission are communicated over differentfrequency resources.
 4. The method of claim 1, wherein the first datatransmission and the second data transmission are communicated over thesame frequency sub-band.
 5. The method of claim 1, wherein the device isa base station or a user equipment.
 6. The method of claim 1, whereinthe first TDD scheduling interval further includes a guard periodseparating the first data transmission and the second data transmissionin the time domain.
 7. The method of claim 1, wherein the first datatransmission or the second data transmission is communicated grant-free.8. The method of claim 7, wherein the first data transmission or thesecond data transmission is communicated in accordance with acontention-based mechanism.
 9. The method of claim 1, wherein the firstTDD scheduling interval is a downlink scheduling interval including anuplink transmission opportunity.
 10. The method of claim 9, furthercomprising communicating, in the downlink scheduling interval, anacknowledgement/negative acknowledgement (ACK/NAK) message traveling inthe uplink direction, the ACK/NACK message confirming whether a previousdownlink data transmission was successfully received.
 11. The method ofclaim 10, wherein the ACK/NAK message and an uplink data transmissionare transmitted over different frequency resources in the downlinkscheduling interval or over the same frequency sub-band during differenttime periods in the downlink scheduling interval, the uplink datatransmission being one of the first data transmission or the second datatransmission.
 12. The method of claim 1, wherein the first TDDscheduling interval is an uplink scheduling interval including adownlink transmission opportunity.
 13. The method of claim 12, furthercomprising communicating, in the uplink scheduling interval, anacknowledgement/non-acknowledgement (ACK/NAK) message traveling in thedownlink direction, the ACK/NACK message confirming whether a previousuplink data transmission was successfully received.
 14. The method ofclaim 13, wherein the ACK/NAK message and a downlink data transmissionare transmitted over different frequency resources during the same timeperiod in the uplink scheduling interval, or over the same frequencysub-band during different time periods in the uplink schedulinginterval, the downlink data transmission being one of the first datatransmission or the second data transmission.
 15. The method of claim 1,further comprising: communicating a third data transmission in a secondTDD scheduling interval configured with a second frame structureconfiguration, the second frame structure configuration being differentfrom the first frame structure configuration.
 16. The method of claim15, wherein the first TDD scheduling interval and the second TDDscheduling interval have different lengths.
 17. The method of claim 15,wherein the first TDD scheduling interval and the second TDD schedulinginterval are assigned to different frequency sub-bands.
 18. The methodof claim 15, wherein the first data transmission in the first TDDscheduling interval and the third data transmission in the second TDDscheduling interval are communicated in accordance with differentsubcarrier spacings, or different cyclic prefix lengths.
 19. The methodof claim 15, further comprising: communicating anacknowledgement/non-acknowledgement (ACK/NAK) message in the second TDDscheduling interval, the third data transmission being communicated in atransmit direction and the ACK/NAK message being communicated in areceive direction, or vice versa.
 20. A method for wirelesscommunications, comprising: assigning, by a network controller, a firstframe structure configuration for communicating in a first time divisionduplexing (TDD) scheduling interval in a first direction over a firstfrequency sub-band, the first frame structure configurationcorresponding to a first set of frame parameters; selecting, by thenetwork controller, a switching type for the first TDD schedulinginterval, the switching type indicating whether or not the first TDDscheduling interval includes at least one transmission opportunity forcommunicating in a second direction, wherein one of the first directionand the second direction being a transmit direction, and the other ofthe first direction and the second direction being a receive direction;and sending an indication indicating communication of orthogonalfrequency division multiplexing (OFDM) signals in the first TDDscheduling interval in accordance with the first set of frame parametersand the selected switching type.
 21. The method of claim 20, wherein thefirst frame structure configuration is assigned in accordance with atraffic type of data communicated in the first TDD scheduling interval,the number of user equipments being served by a base station, a latencyrequirement, or a request from a user equipment.
 22. The method of claim20, wherein the switching type is selected in accordance with the firstframe structure configuration, a latency requirement, or a request froma user equipment.
 23. The method of claim 20, wherein the first set offrame parameters comprises a subcarrier spacing, a scheduling intervallength, an OFDM symbol duration, or a cyclic prefix length.
 24. Themethod of claim 20, further comprising: assigning a second framestructure configuration for communicating in a second TDD schedulinginterval over the first frequency sub-band, the second frame structureconfiguration corresponding to a second set of frame parametersdifferent than the first set of frame parameters.
 25. The method ofclaim 20, further comprising: assigning a second frame structureconfiguration for communicating in a second TDD scheduling interval overa second frequency sub-band, the second frame structure configurationcorresponding to a second set of frame parameters different than thefirst set of frame parameters.
 26. A method for wireless communications,comprising: communicating, by a device, a first transmission in a firsttime division duplexing (TDD) scheduling interval in a first directionin a first frequency sub-band; communicating, by the device, a secondtransmission in the first TDD scheduling interval in a second directionin the first frequency sub-band, one of the first direction and thesecond direction being a transmit direction, and the other of the firstdirection and the second direction being a receive direction;communicating, by the device, a third transmission in a second TDDscheduling interval in the first direction in a second frequencysub-band; and communicating, by the device, a fourth transmission in thesecond TDD scheduling interval in the second direction in the secondfrequency sub-band, the second TDD scheduling interval having adifferent duration from the first TDD scheduling interval.
 27. Themethod of claim 26, wherein the first TDD scheduling interval and thesecond TDD scheduling interval overlap in the time domain.
 28. Themethod of claim 27, wherein the second transmission and the fourthtransmission overlap in the time domain.
 29. The method of claim 28,wherein: communicating the second transmission comprises communicating afirst control signaling; and communicating the fourth transmissioncomprises communicating a data transmission.
 30. The method of claim 28,wherein: communicating the second transmission comprises communicating afirst control signaling; and communicating the fourth transmissioncomprises communicating a second control signaling.
 31. The method ofclaim 30, wherein: the first control signaling and the second controlsignaling are different types of control signaling.
 32. The method ofclaim 26, wherein: the duration of the second TDD scheduling interval islonger than the duration of the first TDD scheduling interval; andcommunicating the fourth transmission comprises communicating the fourthtransmission in a middle portion of the second TDD scheduling interval.33. The method of claim 32, further comprising communicating a fifthtransmission at an end of the second TDD scheduling interval in thesecond direction in the second frequency sub-band.
 34. The method ofclaim 26, wherein the duration of the first TDD scheduling interval isdetermined based on a subcarrier spacing of the first TDD schedulinginterval, and the duration of the second TDD scheduling interval isdetermined based on a subcarrier spacing of the second TDD schedulinginterval.
 35. A method of performing wireless communication, comprising:in a first time division duplexing (TDD) scheduling interval, receivinga data transmission; and in the first TDD scheduling interval,transmitting an acknowledgement (ACK).
 36. The method of claim 35,wherein the ACK acknowledges receipt of the data transmission.